BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / doors_1 / dmail11d.zip / SYSOPMAN.DOC < prev next >

Wrap

Text File | 1992-03-22 | 83KB | 1,525 lines

DataMail Version 1.1 Sysop's Manual Copyright 1991, 1992 Richard K. Naff DataMail Version 1.1 Sysop's Manual: Table of Contents Why DataMail? . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . 1 BBS Specific Files . . . . . . . . . . . . . . . . . . . . . . . 3 System Requirements . . . . . . . . . . . . . . . . . . . . . . . 3 What Are Those Files? . . . . . . . . . . . . . . . . . . . . . . 3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Global Limitations . . . . . . . . . . . . . . . . . . . . . . . 5 Security Level Limitations . . . . . . . . . . . . . . . . . . . 6 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 DataMail Groups . . . . . . . . . . . . . . . . . . . . . . . . . 9 About File Transfers . . . . . . . . . . . . . . . . . . . . . . 9 File Uploads . . . . . . . . . . . . . . . . . . . . . . . . . . 11 File Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . 11 File Downloads . . . . . . . . . . . . . . . . . . . . . . . . . 12 Blocking Uploads of specific Filenames . . . . . . . . . . . . . 12 Force-Deleting Files from Your Disk . . . . . . . . . . . . . . . 13 DMUSRBLD: DataMail Maintenance Program . . . . . . . . . . . . . 13 Post-Caller Maintenance . . . . . . . . . . . . . . . . . . . . . 14 End-of-Day Maintenance . . . . . . . . . . . . . . . . . . . . . 15 On-the-Fly Maintenance . . . . . . . . . . . . . . . . . . . . . 15 DMCHECK: Login-time Check for Pending Files . . . . . . . . . . . 16 DMREPORT: Cross-Referenced Statistics . . . . . . . . . . . . . . 17 DMUTIMSG: UTI Message Builder/Invocation . . . . . . . . . . . . 17 Local Mode from Your BBS . . . . . . . . . . . . . . . . . . . . 19 Local Mode from DOS . . . . . . . . . . . . . . . . . . . . . . . 19 Sponsorship Advertising . . . . . . . . . . . . . . . . . . . . . 20 Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Conversion to Other BBS Software . . . . . . . . . . . . . . . . 23 DataMail Sysop's Manual Version 1.1 Page 1 ====================================================================== Thank you for investigating DataMail. Hopefully, you and your Users will find DataMail to be extremely flexible and supportive. Before getting into the details about running and maintaining DataMail, I would like to strongly encourage you to first read the User's Guide. Remember that as the Sysop, you are also a User of your own BBS. The User's Guide will give you some idea as to what functions DataMail offers and how it works from the User's perspective. In all likelihood (unless you configure it otherwise), DataMail is going to be notifying you sooner or later that one of your Users has uploaded a file for you. At that point, you will need to become "User savvy" anyway, so reading the User's Guide now will certainly not be a waste of time. Additionally, some of DataMail's configuration options might seem a little confusing if you are not aware of their effect on the User's end of things. Why DataMail? ============= Why indeed! I wrote DataMail for the benefit of my Users. I also designed it in such a manner that it would be easy to maintain, flexible when new releases of my BBS software (SpitFire) become available, and portable to virtually all other BBS software packages. The User's Guide details the benefit of DataMail over other related software. It also explains why DataMail is likely to be preferable over the use of "Messages with attached files" if your BBS software happens to support that feature. DataMail is designed to handle virtually any condition that a User might dream-up when it comes to sending and receiving private files, without placing a drain on the Sysop's resources. Legal Notices ============= The DataMail programs, support files, User's Guide, and this Sysop's Manual and its addendums are all copyright 1991 and 1992, Richard K. Naff, all rights reserved. These items may not be tampered with nor altered in any manner for whatever reason. You are granted the express right to distribute these items, provided you observe these constraints: 1) All materials are distributed together as a whole, intact, exactly as you received them. 2) You do not charge a fee of any nature which is directly and specifically related to the DataMail distribution package. If you normally charge a fee for general access to your BBS (or distribute software on diskettes and charge for the diskette and mailing/handling), you are expressly permitted the right to distribute DataMail. However, you are not allowed to attach any unique, special fee for DataMail itself. DataMail Page 2 Version 1.1 Sysop's Manual ====================================================================== DataMail is not free. It is distributed as ShareWare to keep costs down, which in turn means your final price is much lower. You are allowed to evaluate DataMail on your BBS for a period not to exceed 60 calendar days. From the first day you install DataMail, you should decide whether or not you wish to make continued use of it within that 60 day period. After 60 days, you have a 14 day grace period in which to pay for DataMail. After 74 days, if you have not paid for DataMail, you are required to permanently cease using it. Please refer to the Registration/Licensing form at the end of this document. DataMail is not "sold". DataMail remains the sole property of Richard K. Naff at all times. You may obtain a license to use DataMail, but you may not buy the software itself. There is no such thing as a site license. Each set of operational DataMail database files installed require their own license, even if they are installed in a single computer (Multi-node operation is supported by DataMail with one set of operational files). Each other set of operational files requires its own license (even if they are all in one computer). Licenses are granted for the life of the Sysop, but are not transferable. CAUTION: Some States regard the exchange of electronic data as a taxable service if you charge for that exchange. Note that this generally does not apply to "regular" BBS file uploads & downloads; if you charge for access to your BBS, you are usually not included in this tax, if indeed it applies in your State. However, DataMail is a different kettle of fish. Its sole purpose is to exchange files, and to specific individuals at that. If you charge specifically for access to, or use of DataMail, you will most certainly be subject to this tax if your State imposes it! The author is not responsible for collection and payment of any taxes due. You are required to keep your own records and pay your own taxes to your State, in accordance with its laws. You are responsible for knowing and understanding those laws, and for due diligence in determining what those laws are. WARRANTY. DataMail is warranted to not directly manipulate any of your BBS-related files if you have installed it correctly and are using a storage disk & path which your BBS (or other software) does not use. Any corruption to any of your files will either be caused by your UTI programs, power outages, TSR/Device-Drivers, SHARE.EXE, a corrupted DOS Operating System, or misconfiguration. All warranties for compatibility with your specific DOS-based system and/or suitability of purpose are expressly denied. Warranties for loss of information, security restriction malfunctions, disk-access errors, file transfers, and other aspects beyond the control of DataMail and its author are likewise expressly denied. The author's sole liability shall extend to a refund of all monies paid for DataMail licenses, and shall not extend to loss of profits, punitive damages, consequential expenses, nor loss of any information on any computer system which accesses DataMail (directly or indirectly), and the license to use DataMail must be immediately surrendered upon refund of said licensing fees. DataMail Sysop's Manual Version 1.1 Page 3 ====================================================================== BBS Specific Files ================== DataMail is designed to be easily and speedily portable between BBS software. For example, if you are currently using WildCat! and decide to switch to SpitFire, your existing DataMail databases may be converted, intact, to your new BBS software with only minor changes. Specifically, you will be required to rename one program, and purchase a UTI (Universal Text Interface) program for your new software. Beyond that, no changes to, or on behalf of, DataMail are required. Please refer to the addendums for your specific target BBS software. System Requirements =================== You need the following to run DataMail: 1) IBM BIOS Compatible Computer 2) DOS Operating System, 3.1 or higher 3) SHARE.EXE loaded in your CONFIG.SYS 4) ANSI.SYS (or compatible) loaded in your CONFIG.SYS 5) FILES=20 (or higher) specified in your CONFIG.SYS 6) BUFFERS=20 (or higher) specified in your CONFIG.SYS 7) 150K Free Memory after your BBS software is loaded (More if possible to allow longer Receiver Lists) 8) BBS Software which supports the DOOR.SYS file standard What Are Those Files? ===================== DataMail uses several files to get its job done. When you first install DataMail, you will not see all of these files. That's OK. The database files are created only when accessed for the first time, so until all parts of the DataMail door are exercised, some files won't show-up on your disk: DATAMAIL.EXE The DataMail door itself DMUTIMSG.EXE The UTI Message Formatter/Invoker. Run this when there is a DMESSAGE.x file present. DMCONFIG.EXE The Sysop's Configuration program DMUSRBLD.EXE* The User's Database Builder & Maintenance. This file exists only after you have extracted the appropriate file from the BBS- Specific distribution file. This program must exist on your disk by this name. DMREPORT.EXE The Database Reporting Program. Let's you see everything about your Users using Datamail in various aspects, to help you control your Users' use/abuse of DataMail. DataMail Page 4 Version 1.1 Sysop's Manual ====================================================================== DMCHECK.EXE For BBSes which generate a DOOR.SYS at logon time, you can use DMCHECK when the User logs onto your BBS to see if one or more files are waiting for him/her. DMCHECK exits with a return-code of 1 if any files are found. You can check ERRORLEVEL == 1 in your logon batch file, and if true, run DATAMAIL immediately DMXFERS.TXT Text Display for available protocols. DM01CDB.DBD The Database Definition File. This file contains the controlling information about how all other database files are laid out. DM010000.KEY/.DAT The User's Database DM010001.KEY/.DAT The File/Uploader's Database DM010002.KEY/.DAT The Receiver's Database DM010003.KEY/.DAT The Group/Host's Database DM010004.KEY/.DAT The Member's Database DM010005.KEY/.DAT The Sysop's Configuration Database DM010006.KEY/.DAT The Sysop's Security Levels Database DMLOG.x The Audit File for node "x" DMESSAGE.x The UTI Message base file for node "x" DMEXIT?.x One of several files, for node "x" to show how the DataMail door was exited. You can interrogate the presence of these files to know if the User exited normally, dropped carrier, etc. There are additional files, such as the batch files required to perform file transfers. These are all under the Sysop's control, so their names are not shown here. Installation ============ Installation is dependent upon the BBS software you use. They are all pretty much the same on the surface, but there are a few nitty gritty details that are different for each BBS. Please refer to the proper addendum for your BBS software. Currently, only the following BBSes are supported (if yours is not listed, please see the Registration Section of this manual; you could receive a free license for DataMail if you are willing to assist me in getting the proper interface programs written and tested). Please print/review the documentation for your BBS software: BBS Software Addendum -------------------- ------------ PC Board 14.5a PCB145.TXT Remote Access 1.1x RA11.TXT SpitFire 3.x SF31.TXT WildCat! 3.0x WC30.TXT DataMail Sysop's Manual Version 1.1 Page 5 ====================================================================== In all cases, installation involves the following steps: - Define the subdirectory where DataMail files will be stored, and the subdirectory where your Users' Uploads will be stored (and from where other Users will download) - Extract the proper DMUSRBLD.EXE file for your Software - Configure DataMail to read your BBS Master File - Build your initial DataMail User Database - Configure DataMail to point to your chosen directories - Configure DataMail to point to your UTI programs - Configure DataMail for the number of file transfer protocols you wish to use (up to 5), and the path and filename of the batch files which accomplish the file transfers - Establish your file transfer batch files - Provide a text display for each file transfer - "Define" the DataMail door to your BBS +-------------------------------------------------+ | PLEASE PERFORM YOUR CONFIGURATION AT THIS TIME! | +-------------------------------------------------+ Go ahead and get it out of the way, so you may perform Security Level set-ups and other limiting factors without having to deal with any configuration problems or questions. I recommend using my defaults for the time being; once you see how DataMail is supposed to be configured, you can always come back later and change filenames and paths, etc. Global Limitations ================== There are two items you can configure into DataMail which will act as "fail-safes" to prevent total abuse of your disk space. Each of these is accessible in DMCONFIG when you select Configure Global Parameters. MINIMUM REQUIRED DISK SPACE. No matter what, under any circumstances, in any phase of the moon, even if this month doesn't have a "R" in it, this value will guarantee that no one will upload a file which will cause your free disk space to fall below this level. If you have a 100mb disk, and it already has 50mb of data on it, you might try setting this value to 20mb. This will mean that, as long as nothing else adds files to your disk, DataMail will allow 30mb of files to be uploaded and no more. Once the available free disk space reaches 20mb or lower, DataMail stops accepting uploads. No exceptions (not even locally). Whatever value you specify here is sacrosanct. DataMail will never violate this limit. DataMail Page 6 Version 1.1 Sysop's Manual ====================================================================== MAXIMUM RETENTION PERIOD. You will notice in the next section for Security Levels that DataMail will let you specify how long a file may be kept on your disk while waiting for its designated receiver(s) to download it. We'll cover this in more detail in that section, but you should be aware that this value OVERRIDES anything and everything you specify for the individual security levels. If you set this value to 90, for example, then no files will be kept over 90 days. Even if you have a Security Level which stipulates that files may be kept for 120 days, this value overrides that number, and 90 days is the time period that will be used. This value can be used as a fail-safe mechanism just in case you think you might make a mistake while configuring Security Levels. However, it is primarily intended as a short- cut to temporary changes in retention periods. If you suddenly find that you need extra disk space for something else, you can set this value to 5. This will mean that any new uploads will only be kept for 5 days, then they will be deleted. When your disk space becomes free again, raise this value back to 90. The intent is to save you keystrokes by not having to change all your Security Levels to 5 days, and then go back and change them all to their original values. Just change this one value, and you are in business. Security Level Limitations ========================== DataMail uses its own security levels. These are closely tied to the security levels of your BBS, but are not necessarily directly related unless you set them up that way. As distributed, DataMail has only one security level: 0. All users of DataMail will get security level 0 unless you add more levels. The way it works is that DataMail looks at the User's BBS security level, and then finds its own highest security level which does not exceed the security level of the User. For example, assume your BBS has security levels 10, 100, 200, 500, and 900. Assume also that you have configured DataMail to acknowledge security levels 0, 100, and 500. Under these conditions, Users with BBS security level 10 will get DataMail security 0, BBS sec-lvls 100 & 200 get DataMail Sec-lvl 100, and BBS sec-lvls 500 & 900 get DataMail sec-lvl 500. DataMail security level 0 is kind of special. Since all Users (no matter what their BBS security level) will have a BBS security level greater than or equal to 0, DataMail is guaranteed to assign them security level 0 if you have not configured any others. Because of this, DataMail security level 0 must ALWAYS be defined! You will find that you can change the aspects of security level 0, but YOU CANNOT DELETE IT! You will find that all other security levels can be added, changed, and deleted as you like, but security level 0 can only be changed. DataMail Sysop's Manual Version 1.1 Page 7 ====================================================================== When you run DMCONFIG, select Configure Security Levels and you will see a short menu allowing you to Add, Change, or Delete security levels. Their individual functions should be self-explanatory (i.e., "Add" will set-up a new security level, etc.). While working with these functions, keep in mind the Global Limitation pertaining to retention period. It doesn't make any difference what you set the retention periods to for the security levels if the Global value is the lesser; DataMail takes the shortest time period between the Global and security level retention periods. Each aspect of security level values is explained in detail when you select Add or Change, but here they are in a nutshell: RECEIVER'S SECURITY LEVEL. This value refers to the receiver's BBS security level. The designated receiver must have a security level equal to or greater than the value you specify here, otherwise DataMail will not let the current User upload to that receiver. For example, let's say your new, unverified callers are assigned security level 10 on your BBS, and you are setting up DataMail security level 10 at the moment. If you do not want these new, unverified callers uploading to other new, unverified callers, set this value to at least 11. In that case, when a User of BBS/DataMail security level 10 tries to upload to a receiver of BBS security level 10, DataMail will tell them they are not allowed to do that and will ask them for another name (or quit). Unless you have oodles of disk space and don't care about who calls your BBS, I strongly recommend this for new, unverified callers. Otherwise, you are likely to find that all that free disk space has suddenly disappeared! NUMBER OF OUTSTANDING FILES. This value limits the number of files a User can have sitting on your disk at any one moment in time. More precisely, it limits NEW files. If you let John Doe upload 5 files a few days ago, then change his DataMail security level entry to allow only 3 files, John cannot upload any more NEW files. He can, however, OVERLAY any of his existing 5 files as long as they are on your disk. RETENTION PERIOD IN DAYS. This value is "attached" to a file at time of upload or overlay. Changing this value AFTER a file is already on your disk does not change the retention period of that file (retention periods are assigned after a successful upload, and are not reassigned at any other point). When you run DMUSRBLD for your daily maintenance, this date is checked with today's date. If today is "greater" than the retention period date, the file is automatically purged from your disk. DataMail Page 8 Version 1.1 Sysop's Manual ====================================================================== MAXIMUM FILE SIZE. This file limits the size of any single file uploaded. It does NOT represent the "total allowed bytes of all files uploaded by a User". It affects only one file at a time. If you have a security level for which you do not want Users uploading at all, I recommend setting this value to 0. If so, a user of this DataMail security level will not be able to upload. They WILL be able to download any files that someone sent to them, but they cannot upload. That about wraps it up for Configuring DataMail. Your Global configuration values should stay fairly static unless you rename directories (which I don't recommend). If there's any tweaking to be done in terms of reaching a happy compromise between your Users' needs and your disk space, you will find that the Security Level Parameters are normally the place to turn. The above limitations should be flexible and rich enough to allow you to limit your Users' use of DataMail to the point that they get what they need, but you aren't subjected to abuse of your disk space. Monitoring ========== Congratulations! DataMail is now fully operational on your BBS! Things you might want to do in the first week or two of use, or on a regular monthly basis: 1) Monitor your uploads. Check to see how many files people of each security level are uploading, and each file's size. Compare this with your available disk space, and make adjustments in your Security Level Configurations. 2) If you operate a multi-node system, iron the bugs out of your set up and your batch files for file transfers. When your first node is running smoothly, set up a DM2.BAT, etc., file to handle other nodes, and define the DataMail door to your BBS software so that other nodes can run DataMail. No changes (other than DM2.BAT, DM3.BAT, etc.) should be required for DMCONFIG; everything should remain identical across all nodes. The only changes should be to your BBS software (defining a new door to your other nodes). 3) Monitor your new callers! If you don't care that new people will be calling just to use DataMail to exchange files with their buddies across town, then skip this. But if you have left DataMail wide-open to unlimited use, you might find your disk space rapidly dwindling! If so, go back and place some tighter restrictions on who can upload to whom, and how much at any one time. Cut back on new callers' abilities until they have been "verified". Reduce the retention period for files uploaded by new callers. DataMail Sysop's Manual Version 1.1 Page 9 ====================================================================== DataMail Groups =============== DataMail Groups are explained in the User's Guide. You are not required to support these, but it will provide your Users with added benefits if you do. In other cases, you (as both Sysop and User of your BBS) may wish to make a certain set of files available to only a select few individuals. In this case, it's a whole lot easier to define a DataMail Group with a list of "permanent" names and "upload" your file(s) to that Group. Without Groups, you would have to manually type every receiver's name each time you had a file you wanted to send to them. DMCONFIG lets you Add & Delete DataMail Groups. Only DMCONFIG can be used to Add and Delete Groups; the DataMail door program will let you or your designated Group Host Add & Delete Members of a Group. DMCONFIG also lets you establish a User of your choice as the Host of that Group. You, as Sysop, are always a Host of every Group, in addition to any User you set-up as Host. If the Group you define is for your own needs (private files from you to your Users), you will probably NOT want to establish a Host for the Group. In other cases, where you have a few Users who happen to use your BBS as their "Home Base" for communicating with each other, you might want to define one of those Users as the Group's Host. The only added function a Host of a Group has is that he/she is able to add or delete Members of that Group. Other than that, a Host has no special privileges in DataMail. A HOST IS NOT A MEMBER OF A GROUP BY DEFAULT. If the Host wishes to send or receive files via the Group, he/she MUST add their own name as a Group member. Users cannot upload to a Group if they are not a member of that Group. Users who are not a member of a Group will not receive a copy of a file uploaded to that Group. In a nutshell, file uploads to Group members can only occur if all persons involved are members of the Group. Hosts (you as Sysop, and any other User you define as Host) are not automatically members of a Group. About File Transfers ==================== DataMail uses batch files for file transfers. You are free to use whatever protocol you wish in those batch files; DataMail doesn't care. Based upon your Global Configuration and the protocol selected by the User, DataMail will spawn a batch file and pass the following (all values other than the first 2 are acquired from the DOOR.SYS file): - An "R" or an "S", which denotes whether a Receive or Send should be accomplished. Simply "goto" a label in your batch file which handles uploads or downloads, respectively. DataMail Page 10 Version 1.1 Sysop's Manual ====================================================================== - The full path and filename of the file to be uploaded or downloaded. This consists of the path you defined in your Global Configuration where files are to be stored, followed by a "\", followed by the name of the file the User is attempting to transfer. For UPLOADS only, the filename is ALWAYS DATAMAIL.x, where "x" is your Node number. After a successful upload, this file is renamed to the name the User asked for. Downloads ALWAYS represent the exact filename to download. - The Communications port number (e.g., 1 or 2, etc.) with which the current Node is associated. - The DTE/DCE bps rate. This is the bps speed at which your computer is communicating with your modem. For Sysops who lock their DTE/DCE speed to a constant value (such as 19200 or 38400), you should use this parameter for your protocol program. If necessary, tell your protocol program you are using Hardware data-flow control (RTS/CTS). - The Modem/Modem rate. This is the bps rate at which your modem and the caller's modem are actually communicating, regardless of whether you or your User have their DTE/DCE speeds locked. If you do not lock your DTE/DCE speed, then more than likely your modem (and your BBS software) adjusts to this speed. In that event, this is the parameter you should pass to your protocol program. If necessary, tell your protocol program you are using Software data-flow control (Ctrl-S/Ctrl-Q, otherwise known as XON/XOFF). - The UART base address of the communications port in use, in HEXADECIMAL notation. If you use a non-standard communications port (i.e., you cannot simply get by with a plain COM1 or COM2 device name), this value should be passed on to your protocol program IF IT REQUIRES THE UART BASE ADDRESS IN HEXADECIMAL FORMAT. - The UART base address of the communications port in use, in DECIMAL notation. This is just like the above parameter, except it is in decimal notation (base 10). Use this parameter IF YOUR PROTOCOL PROGRAM REQUIRES THE UART BASE ADDRESS IN DECIMAL FORMAT. - The IRQ number to be used in combination with either of the above to parameters. If you supply either of the above parameters to your protocol program, more than likely it will also require the IRQ number. In that event, pass this parameter to your protocol program. DataMail Sysop's Manual Version 1.1 Page 11 ====================================================================== File Uploads ============ During a file upload (uploading a NEW file to 1 or more receivers), the following events occur: - Before the batch file is spawned, file DATAMAIL.x (where "x" is the current Node number) is deleted if it exists. - The batch file is spawned to handle uploads. You should check the return code from your protocol program! If there was an error, you should DEL %2 (or ERASE %2, whichever you like best). When DataMail regains control, it will check to see if DATAMAIL.x exists. If it does, DataMail assumes the file was uploaded successfully. - If DATAMAIL.x exists in your DataMail Files directory, it is renamed to whatever the User wants it to be called. - DataMail then checks the size of the newly received file. If it is larger than that allowed (based on your configuration and free disk space), it is immediately deleted. - Each person in the receiver list for this file is issued a message telling them that a new file is waiting for them to download. File Overlays (Uploads of Existing Filenames) ============================================= During an Overlay (re-uploading a file by the same name, from the same User who uploaded the original file by that name), the following events occur: - Before the batch file is spawned, file DATAMAIL.x (where "x" is the current Node number) is deleted if it exists. - The batch file is spawned to handle uploads. You should check the return code from your protocol program! If there was an error, you should DEL %2 (or ERASE %2, whichever you like best). When DataMail regains control, it will check to see if DATAMAIL.x exists. If it does, DataMail assumes the file was uploaded successfully. - If DATAMAIL.x exists in your DataMail Files directory, the original file is deleted, and DATAMAIL.x is renamed to the old, original filename. - Anyone who was ADDED to the receiver list of this file is issued a message telling them that a new file is waiting for them. DataMail Page 12 Version 1.1 Sysop's Manual ====================================================================== - Anyone who was left "intact" in the receiver list of this file is issued a message telling them that the original file was overlaid, and a new copy is available. - Anyone who was REMOVED from the receiver list of this file is issued a message telling them that the Uploader deleted the file, and it is no longer available for them to download. File Downloads ============== After a file is successfully download: - DataMail sends a message to the Uploader, informing him/her that the file was received properly. - DataMail removes the Current User from the receiver list of this file. - DataMail then checks the receiver list for this file. If there are not any additional receivers, DataMail removes this file from its database, and physically deletes this file from your disk. - DataMail then checks to see if there are any more files waiting to be downloaded by the Current User. Blocking Uploads of specific Filenames ====================================== DataMail checks for duplicate filenames in two ways. First, it checks its own database for the Current User to see if that User has already uploaded a file by the specified name. Next, it checks your DataMail File directory to see if a file by that name exists. In the latter case, DataMail will tell the User that he/she cannot upload a file by that name, because one already exists. This feature is provided for those Sysops who do not want Users uploading files by the names of COMMAND.COM, CONFIG.SYS, etc. To prevent such filenames from being uploaded, all you have to do is define a file by the target name in your DataMail Files directory. It does not have to be the actual file itself (i.e., the CONFIG.SYS file could simply contain "ABC"), but it must be of a length greater than 0. DataMail Sysop's Manual Version 1.1 Page 13 ====================================================================== Force-Deleting Files from Your Disk =================================== If there is a file on your disk that you want to get rid of right NOW(!), just delete it. DataMail can gracefully handle this situation (i.e., it thinks the file should be there, but it really isn't). Note that it would be best to run DMUSRBLD immediately after deleting files in this manner; doing so will inform the Receivers that the file was deleted, and DataMail will have a chance to clean-up its own database to bring it into synchronization with the "real world". Please see the On-The-Fly Maintenance section for more details. DMUSRBLD: DataMail Maintenance Program ====================================== DMUSRBLD is customized for each BBS software package. This is the program you extracted during installation. DMUSRBLD accomplishes the following functions: - If DM010000.KEY/.DAT do not exist, DMUSRBLD creates these files. These files contain information about your BBS Users (their Name, Security Level, etc.). This is referred to as "Create" or "Rebuild" mode, and can take a long time depending upon your CPU and disk speed. - If DM010000.KEY/.DAT already exist, DataMail takes the date of last update to this file, then scans your BBS Master File for any Users who have a "last called" date greater than or equal to the database's last update date. For each such User found, DataMail retrieves their record from its database and compares the information it knows about with your BBS Master File. If anything about that User has changed, his/her information is updated in the DataMail databases. This is referred to a "Refresh" mode and only requires a few seconds to accomplish. - Each file in the DataMail databases is checked. If the file does not physically exist on your disk (you deleted it), DataMail sends a message to all remaining receivers to inform them that the file is no longer available. Each Receiver is checked to make sure he/she is still a valid User of your BBS. If not, their name is removed from the receiver's list (and the file physically deleted if that was the last receiver). Finally, each file is checked for its expiration date. If "today" is greater than the file's expiration date, the file is physically deleted and all pending receivers are sent a message informing them of that. - Each Group is checked to make sure that Hosts and Members are still valid Users of your BBS. Those that aren't are removed as Host and/or Member as appropriate. DataMail Page 14 Version 1.1 Sysop's Manual ====================================================================== When DMUSRBLD runs, you should pass it the Node number you are running it from. In other words, if you run DMUSRBLD from Node 1 of your BBS, you should run it as "DMUSRBLD 1". The reason for this is so that any messages created for Uploaders and/or Receivers are placed in a file called DMESSAGE.x, where "x" is your Node number. If DMESSAGE.x already exists, any new messages are ADDED to it, so the next time you run DMUTIMSG, all messages created by either the DataMail door itself, or DMUSRBLD, are imported into your BBS message bases. Note that it is perfectly acceptable to run DMUSRBLD with a non-existent Node number (such as 0). In fact, if you do not provide a Node number to DMUSRBLD, this is the "Node" assumed, and DMESSAGE.0 will be created if necessary. You can still run DMUTIMSG and tell it to use DMESSAGE.0 without any problems. The main reason for using a legitimate Node number is to make sure your have an event somewhere that will guarantee any and all DMESSAGE.x files are processed by DMUTIMSG. Also, if you run a multi- node system, you should not be placing messages into DMESSAGE.2 if you are not running under that node at the current time; if there is a user logged onto Node 2 and running DataMail right now, the messages created by DMUSRBLD might "step on" the messages created by the User of the DataMail door. Post-Caller Maintenance ======================= As a personal preference, I run DMUSRBLD after each caller logs off. This has the effect of adding a new caller to the DataMail databases immediately. It also has the effect of upgrading the "known" BBS security level of a caller if he/she did something on the BBS just now to increase or decrease his/her security level. If you wish to do this also, make sure you use the correct Node number (if you run a multi-node BBS). For example, when a User logs off of Node number 1, your logoff batch file should say "DMUSRBLD 1". If it was Node number 2 that the User logged off of, your logoff batch file should day "DMUSRBLD 2", etc. Note that running DMUSRBLD after each caller logs off is simply a matter of preference for the Sysop. Whatever information DataMail received the last time you ran DMUSRBLD will still be in effect, and since it is likely to change very little in a single day, there shouldn't be any critical information missing. DataMail Sysop's Manual Version 1.1 Page 15 ====================================================================== End-of-Day Maintenance ====================== At midnight (or close thereafter), you should run DMUSRBLD from at least one of your BBS Nodes (if you only have one, that's the guy you want). Your midnight batch file should say "DMUSRBLD x", where "x" is the node number you are running from. You should follow this with a: IF EXIST DMESSAGE.x DMUTIMSG DMESSAGE.x y z The above checks for any messages that DMUSRBLD created, and runs the DMUTIMSG program to import those messages into your BBS message base. Running DMUSRBLD at midnight is highly recommended. You don't have to, but since DMUSRBLD deletes files (for various reasons), you won't be "up to date" in terms of expired files or invalid receivers. Running DMUTIMSG is not as critical, and you can skip it if you have no interest in importing any messages that DMUSRBLD may have created. On-the-Fly Maintenance ====================== While getting your DataMail Users Database (DM010000.KEY/.DAT) created was accomplished at installation time, and "refreshing" that database can be done after each caller logs off (or at midnight, if you prefer), there are reasons why you should force-rebuild DM010000.KEY/.DAT. If you perform any of the following maintenance to your BBS Master File, you should (as soon as possible) take all BBS Nodes off-line, delete DM010000.KEY/.DAT, and run DMUSRBLD: - Manually alter a User's Security Level/Lock-out Flag/Deleted Flag, etc., WITHOUT changing their Last-Call Date (if the Last-Call Date was prior to "today") - Restore from a back-up copy - "Pack" or physically remove logically deleted Users In some cases, DMUSRBLD is able to detect that you have made "serious" changes to your BBS Master File, and will delete DM010000.KEY/.DAT and rebuild it automatically. In other cases, changes to your BBS Master file are difficult to detect in "Refresh" mode, and DMUSRBLD might not know that it is dealing with major changes. The "Refresh" mode is intentionally "unintelligent" in the interest of making it run as fast as possible, applying only minor changes (like a new user, or a user who has been locked-out while online or had their security level changed). To make sure DMUSRBLD establishes DM010000.KEY/.DAT which represents the "real" BBS Master File, you should perform the above maintenance whenever you make any of the above changes to your BBS Master File. DataMail Page 16 Version 1.1 Sysop's Manual ====================================================================== Generally, any of the above modifications should be made when all BBS Nodes are off-line, so it is a good idea to go ahead and perform this DataMail maintenance at the same time. DMCHECK: Login-time Check for Pending Files =========================================== Not all BBS software packages create a DOOR.SYS immediately upon a User logging into your BBS. For those that do NOT create DOOR.SYS at login-time, this program is of little use, but please keep reading; it might still serve you well! When your BBS executes its login batch file (right after a user successfully logs into your BBS), you can run DMCHECK. To see the arguments required and DMCHECK's return-code values, just run DMCHECK with no arguments at all. When you run DMCHECK in your login batch file, it makes a quick scan of the DataMail Files database to see if the current User has one or more files waiting to be downloaded. If so, DMCHECK exits with return-code of 1. You can then force an execution of the DataMail door via: DMCHECK DOOR.SYS IF ERRORLEVEL == 1 CALL D:\DATAMAIL\DMx.BAT ..... Basically, this forces Users to run DataMail if they have files waiting for them. This helps to get those files off your drive much faster. If your BBS does NOT create DOOR.SYS at login time, you can still use DMCHECK in all of your other door batch files. Basically, no matter what door the User runs, you can place DMCHECK in all those batch files (before or after the door supposed to be run from that batch file). In that event, no matter what door the User runs, you can force the User to download his files from DataMail and get them off of your disk. In other words, say you run the TradeWars door. Inside the batch file that gets your TradeWars program running, insert the above lines (the ones that run DMCHECK and then test ERRORLEVEL). Insert those lines either before you run the TradeWars program or after; it doesn't matter. By placing the above lines in your TradeWars batch file, you can force your Caller to check for any files in DataMail whenever they run TradeWars. Do the same for all your door batch files, and no matter what door the Caller runs, you can force them to run DataMail and download their file(s). DataMail Sysop's Manual Version 1.1 Page 17 ====================================================================== DMREPORT: Cross-Referenced Statistics ===================================== DMREPORT provides you with a way to peek inside the DataMail databases and see what is there. The reports are sent to stdout (i.e., your terminal), so you can redirect the output to a file or your printer via the DOS ">" redirection operator. DMREPORT provides 3 categories of reports: Users, Files, & Groups. There are a total of 7 reports available, numbered, coincidentally, from 1 though 7. To get a particular report, you run "DMREPORT y" where "y" is the report number you want. DMREPORT can handle multiple reports from a single execution. If you want reports 2, 3, and 4, you can execute "DMREPORT 2 3 4" and all three reports will be produced. Because of this ability (and because you can redirect the output to your printer), DMREPORT issues a final form- feed character at the end of each report. This will cause your printer to advance to the top of the next page after each report has been produced. Report 1 simply generates a list of known BBS Users and their security level. I admit this is of little use on a daily basis, but it does come in handy after you rebuild DM010000.KEY/.DAT to make sure that these files were properly created. Reports 2, 3, and 4 give you information about each file, uploader, and receiver. They come in handy when you need to know what files DataMail knows about, who has uploaded what, or who is waiting to download what. Reports 5, 6, and 7 deal with Groups, Hosts, and Members. This lets you readily see what Groups you have defined, what Groups each User is a Host of, and what groups each User is a member of. If your Group Host or Members are complaining that things don't seem to be working correctly, these reports may help you isolate any problems in your set-up. DMUTIMSG: UTI Message Builder/Invocation ======================================== DMUTIMSG serves two purposes. The first is to take the "shorthand" messages created by either DATAMAIL or DMUSRBLD and expand them into full-blown text messages, suitable for processing by UTIIMPRT.EXE. The second is to spawn UTIIMPRT.EXE which will actually import the desired messages into your BBS messages base. DMUTIMSG is run with either 2 or 3 arguments: DMUTIMSG DMESSAGE.x n -or- DMUTIMSG DMESSAGE.x n Y DataMail Page 18 Version 1.1 Sysop's Manual ====================================================================== The "x" is the Node number which created DMESSAGE.x. If you follow my recommendations in setting up DataMail, Node 1 will create DMESSAGE.1, Node 2 will create DMESSAGE.2, etc. DMUSRBLD will create either DMESSAGE.0, or DMESSAGE.x if you supply a Node number as an argument to DMUSRBLD. If you are running a multi-node BBS, you should only process the DMESSAGE.x file which is associated with the Node number that you are running DMUTIMSG from. If you are running from the DOS command-line, you can execute DMUTIMSG for any DMESSAGE.x file, as long as there is no one currently logged onto those Nodes. The "n" in the above files varies from BBS to BBS. Some BBS software keeps all messages in a single directory, and has a bunch of files named something like "MSG01.KEY/.DAT, MSG02.KEY/.DAT", etc., for as many message bases as your have. If this describes your BBS (e.g., SpitFire), then "n" is the message base number into which you want your DataMail messages imported. For example, if you want your messages imported into message base 14, then "n" is 14. For other BBS software packages (e.g., PCBoard), "n" is a directory name. BBSes like this have one subdirectory for every message base, and each subdirectory has files named something like "M1.TXT, M2.TXT, ... M9999999.TXT", etc. For this type of BBS, "n" will likely be the SUBDIRECTORY name. For example, if your subdirectories are called C:\BBSMSGS\MSGS01, C:\BBSMSGS\MSGS02, etc., for message bases 1 & 2, then "n" will be C:\BBSMSGS\MSGS02 if you want DataMail messages imported into message base 2. The easiest way to find out which you should be using is to run your UTILIST program. Run it as "UTILIST TEMP.LST". Then take a look at the contents of TEMP.LST. Each message base your BBS supports requires three lines of information in TEMP.LST. Look at lines 1, 4, 7, 10, etc. If you see a simple number on these lines, then you should run DMUTIMSG where "n" is a number. If you see directory names, then you should run DMUTIMSG where "n" is a directory name. The 3rd argument is optional. If present, it must be an uppercase "Y" (no quotes, just the letter Y). If it is not a "Y", it is simply ignored. The purpose of this optional parameter is to let you mark your DataMail messages as e-mail messages (i.e., they will be echoed on a national network). The messages will be echoed onto that network if you are connected to it, and if the conference number into which you import DataMail messages is configured as an e-mail message base. This might come in handy if someone on a network calls your BBS long distance and uploads a file to 1 or more people. When those receivers download the file, DataMail will send a message to the Uploader to let him/her know that each receiver successfully downloaded the file. By marking the DataMail messages as e-mail, the receipt-acknowledgement messages will be echoed onto the network so your long-distance caller will know when (if) his uploaded file was received. DataMail Sysop's Manual Version 1.1 Page 19 ====================================================================== All messages imported into your BBS message base have the following information somewhere within them: - Uploader's Name - Receiver's Name - Filename - "Status" or "Function" performed - Date and Time "Function" was performed Some messages (like Upload/Overlay) contain the 2-line description of the file. In most cases, the message is addressed TO and FROM the Uploader/Downloader or Downloader/Uploader, depending upon which "way" the message is directed. In other cases (like an expired file which is deleted), the message is FROM "DATAMAIL". All messages are sent as Receiver Only ("Private"). Local Mode from Your BBS ======================== If you, as the Sysop, wish to use DataMail "locally" to send or receive files, and you are logged into your BBS, all you have to do is run your DataMail door just as any User would. No special considerations need be given as long as you are logged into your BBS and running DataMail from there. When you do, all rules that apply to a Remote User apply to you (DataMail considers you to be just another User). There are, however, a couple of differences. First, you will see two additional options that Remote Users don't see and can't execute. These are a shell to the DMCONFIG and DMUSRBLD. You may run either of these programs directly from the DataMail door if you wish to. Secondly, your "uploads" and "downloads" work a little differently. The difference is that the file transfer batch files are not spawned. You are asked for the Drive:\Path\Filename to "upload" or "download", and a low-level DOS copy is performed to copy files into and out of the DataMail Files directory. Checks for file existence and file size still apply; you cannot "upload" a file that is larger than your allowed size. If you need to "upload" a really big file, use the Shell to DMCONFIG option and set yourself up with a Security Level that allows bigger files. When you return to the DataMail door, you will then be allowed to "upload" bigger files. Local Mode from DOS =================== Please review the above section for operational differences of the DataMail door when running in local mode. DataMail Page 20 Version 1.1 Sysop's Manual ====================================================================== There is a special requirement for running DataMail from the DOS command-line. DataMail requires a DOOR.SYS file at all times. The simplest way of establishing a "fake" DOOR.SYS is to run DataMail once from your BBS (see the previous section) and then exit back to your BBS. From your BBS, "shell to DOS". While in DOS, copy the DOOR.SYS file to your D:\DATAMAIL directory and call it something like LOCAL.SYS or NODE0.SYS. Return to your BBS (by typing EXIT on the DOS command line), and then, finally, logoff of your BBS. Now, go to D:\DATAMAIL, crank-up your text editor, and create a batch file called LOCAL.BAT or perhaps DM0.BAT. Place the following in that batch file: D: CD \DATAMAIL DATAMAIL LOCAL.SYS (or whatever you called DOOR.SYS) IF EXIST DMESSAGE.0 DMUTIMSG DMESSAGE.0 n The "n" in the last line above is explained in the section for DMUTIMSG. One more change and then you are done. While you have your text editor running, edit LOCAL.SYS (or whatever you called it). Look at line 4. If you just created LOCAL.SYS by logging onto your Node number 1 of your BBS, this line will have a 1 in it. If your ran from Node number 2, this line will have a 2 in it, etc. Whatever that number is, change it to 0 and then save LOCAL.SYS. That's all. Now, you should be able to simply type DM0 from the DOS command-line and DataMail should run just fine for you. Note that you do not have to use Node number 0 for this purpose. You can just as easily use Node number 999 or some other ridiculously large number. Whatever Node number you choose, make sure that LOCAL.SYS (line 4) and DMESSAGE.x have the same Node number. Sponsorship Advertising ======================= There is a new phenomenon taking hold across the country where BBS Callers pay to purchase software for the Sysop. I am happy to see this new "Share and share alike" attitude spreading. One consideration though, and that is that most Callers who buy software for their Sysop expect to have their name prominently displayed for all other Callers to see. Who can blame them? If a Caller wishes to buy software for use by the Sysop and other Callers, it is certainly not an outrageous demand that they get the credit for it. DataMail offers a feature whereby you, the Sysop, can establish one or more "Advertisement" files, one of which will be displayed each time the DataMail door is started. What you put in those files is your business - the intent was to let you say something like "This Door is brought to you by Joe Caller", but you can use this feature for displaying a newsletter, fancy ANSI graphics, or whatever else you wish the Callers to see when they run DataMail. DataMail Sysop's Manual Version 1.1 Page 21 ====================================================================== To use this feature, you need to create one or more files called "DMAD", "DMAD.G", "DMADssss", and/or "DMADssss.G". The "ssss" portion of the last two filenames is supposed to be replaced by the various numerical security levels you have available. To illustrate how this works, suppose you logon as "Sysop" (or whatever name you usually use) and you have a security level of 99. When you run DataMail, it looks for the DMAD*.* files in this order: If you have ANSI graphics (color) turned on, DataMail looks for DMAD99.G If it cannot find this file, then it looks for DMAD99 If it cannot find this file, then it looks for DMAD.G If it cannot find this file, then it looks for DMAD If it cannot find this file, nothing is displayed. If you do not have ANSI graphics turned on, DataMail looks for DMAD99 If it cannot find this file, then it looks for DMAD If it cannot find this file, nothing is displayed. In brief, DataMail gives first priority to finding a file by the name of DMADssss.*, and within that priority, it tries to use the ANSI graphics file if it exists and if you had ANSI graphics turned on when you first started DataMail. So, for example, if there's a "catch-all" file that you want to make sure everyone sees, call it DMAD (and/or DMAD.G for ANSI). However, if certain security levels should see a different file than most other Callers, set-up the appropriate DMADssss (and/or DMADssss.G). On the other hand, perhaps there are security levels (like yours) that you don't want to have such a file displayed. In this case, just make sure that DMAD and DMAD.G do not exist. Set-up DMADssss and DMADssss.G for all your security levels, except for the security levels that you do not want to see the display. What goes in those DMAD*.* files? Basically, anything you want. There are only two reserved characters that cause the display to behave differently than simply copying the file to the Caller's screen. These two characters are Ctrl-P and Ctrl-Z. These are not normally considered "typing" characters, and do not naturally appear in ANSI graphics files. The purposes of these two characters are: - Ctrl-P is used as a "Pause" character. When encountered in your DMAD*.* files, the process of displaying the file comes to a halt and waits for the Caller to press "Enter". The Ctrl-P character itself is not transmitted - it is completely removed from the display. If you like to set-up ANSI displays that use "Sprite Graphics" ("moving" characters) or happen to be several screens in length, then you might want to imbed a Ctrl-P character at strategic points in order to let the Caller view what is on the screen before it gets erased with more information. DataMail Page 22 Version 1.1 Sysop's Manual ====================================================================== - Ctrl-Z is taken to be the End-of-File character. This character normally appears at the end of every DOS ASCII file, and when DataMail encounters it, the display process is terminated. Note that, if a DMAD*.* is found (according to the above rules) and displayed, there is an automatic halt built-in to DataMail upon reaching the end of the file. Do not imbed a Ctrl-P character at the end of your file! Doing so will force the Caller to press enter once (to respond to the Ctrl-P), and then once more (to respond to the end- of-file condition). The final pause is built-in so that your display file doesn't just "flash" by the Caller without them having a chance to view it. Note also that DataMail will not prompt the Caller to press "Enter" when it pauses. Doing so could mess-up a really great ANSI graphics file, so I chose to leave out any automatic prompting. If you feel a prompt is needed, just add one yourself in your DMAD*.* files (just before any Ctrl-P character, and again as the very last thing in your file). Hopefully, this feature will tilt the scales for you if there is a Caller who is considering purchasing DataMail for you, but is a little hesitant because he/she won't get any public credit for doing so. The DMAD*.* files will let you give credit where it is due! Oh, by the way... if you don't want this feature, just don't define any DMAD*.* files - if they aren't available, there are no start-up pauses, no delays. The Callers go straight into DataMail. Registration ============ As noted earlier, you cannot buy DataMail; you purchase a license in perpetuity to use it. A licensing fee is required for each operational set of DataMail files you use, regardless of how many computers and/or disks are involved. If you run a multi-node BBS, but only have one set of operational DataMail files, you only need one license. Licenses are issued for the life of the BBS Sysop in whose name it is issued. It is non-revokable, but likewise it is non- transferable (you cannot sell, trade, or give away your license). The current licensing fee for DataMail is $20.00 (subject to change without advance notice), payable in U.S. funds only. Students are given a discount for good grades. License fees for students are as follows: GPA = 95 or higher (A): $8.00 GPA = 90 or higher (B): $10.00 GPA = 85 or higher : $12.50 GPA = 80 or higher (C): $15.00 DataMail Sysop's Manual Version 1.1 Page 23 ====================================================================== To qualify for this discount, you must enclose a photo copy of your last 2 report cards/grade marks. All GP's for both sets of marks will be added together and divided by the number of marks. The result (the average) will be the level you qualify for. Incomplete courses will be counted as GP = 0. Discounted licenses for DataMail will have a registration identifier in the name of the Student; no customized registration identifier is available for discounted licenses. However, if you wish to obtain a customized registration identifier at a later date, you may pay the difference between your original cost (as detailed above) and the current price for DataMail in its non- discounted form. The copies of marks you submit must be the most recent markings you have received. Sending a copy of markings from 18 months ago qualifies you for 0 discount. Any obvious tampering (in my judgement) qualifies you for 0 discount. If you wish to ensure your marks are judged as legitimate, have the copies notarized. Site-licenses are NOT available. Each operational set of DataMail files requires a $20.00 licensing fee. Your registration identifier may be obtained either by calling my BBS and downloading it, by diskette via U.S. Mail (additional charge for diskette and postage), or by having me call your BBS and uploading it (pre-payment of LD fee & pre-established account on your BBS required). This identifier will display on your screen in place of the "Not Registered" message. You may have this customized to your liking; anything from your name, to your BBS's name, to "The Man in the Moon". Conversion to Other BBS Software ================================ If you currently run a BBS that supports DOOR.SYS, but for which there is not yet a DMUSRBLD.EXE program (or you are getting ready to switch to such software from your current BBS and want to be able to run DataMail for that software also), you may be able to obtain a free license for DataMail. I offer a free registration to the first Sysop of a not-yet-supported BBS package who is willing to assist me in porting DataMail to it. Basically what is involved, is that I need to create a DMUSRBLD.EXE program for your BBS software. To do this, I will need a significant amount of information from you about that software. Such items will include the file layouts of the BBS Master File, how a new door is "added" or "defined" to that BBS, etc. You will also have to locate a UTI package for your BBS package if you want to import DataMail messages into your BBS message bases. DataMail Page 24 Version 1.1 Sysop's Manual ====================================================================== Please write for details. Include your mailing address and daytime, evening, and weekend phone numbers. Creating a new DMUSRBLD.EXE program will be the major hurdle, and once that is completed, you may easily run DataMail on your new BBS. However, in the interest of providing proper documentation, I will also require that you review and correct my installation procedures for your BBS software. In some extreme cases, I will require that you provide me with a sample BBS Master File with dummy Users who exhibit all possible combinations of security levels and status-flags. The actual work you will have to perform is research and documentation correction, along with verification that the new DMUSRBLD.EXE program is working properly for your BBS. My work will be to write the code for your new DMUSRBLD.EXE and provide drafts of documentation for your review. Once successfully ported, you will receive a free license for DataMail. If you have already registered DataMail for your "old" BBS, I will refund the licensing fee you paid. Note, however, that refunds of shipping fees or Long-Distance phone calls are NOT given; just the basic licensing fee for DataMail. DataMail Registration Form (one per license, please) Name _________________________________________________________________ Mailing Address ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ [ ] I am registering DataMail version 1 at $20.00 [ ] I am a student, applying for my registration at $__________. I have enclosed a copy of my 2 most recent markings, and according to the Sysop's Manual, Registration Section, I calculate my GPA to be _______. If this is not correct, I authorize you to return my registration fee immediately. I would like my Registration Identifier to read (not available for Student discounts - whatever you place in the "Name" field above is what your Registration Identifier will be): ______________________________________________________________________ (maximum 60 characters, including spaces, and no double-quotes) [ ] I will call your BBS (214-398-3112) and download my Registration Identifier. I understand that I must call NOW and establish an account. I will allow 14 days for my registration fee to reach you, and I will call after that time to download my Identifier. [ ] Please send me my Registration Identifier on 3.5" 720K diskette (add $7.00 for U.S. destinations, $10.00 for international). [ ] Please send me my Registration Identifier on 5.25" 360K diskette (add $5.00 for U.S. destinations, $8.00 for international). [ ] Please call my BBS and upload my Registration Identifier (add $4.00 for Texas numbers, $3.00 for continental U.S., $6.00 for Alaska/Hawaii/Puerto Rico/Canada, $12.00 all others). I have already established an account for you on my BBS (use back of this form to explain LogonID, Password, & procedures to log into your BBS). I understand that you will attempt to call until my BBS answers, but if I have not provided you with the correct information and you cannot logon as directed, you will not call again, but will immediately refund my registration fee, less the additional money for the pre-paid long-distance charge. Please remit all monies in U.S. funds only to: Richard K. Naff 2023 Shortal Drive Dallas, TX 75217-1834 U.S.A. DataMail Problem Report Please use this form to report operational problems with DataMail. I will respond to messages left on my BBS (214-398-3112), and to those left in RIME (Node ->DFWPGMR) SpitFire Software, SpitFire Sysops, and Sysops conferences, but the following information is required no matter if you mail this form or leave electronic mail for me: DataMail Version Number: _____________________________________________ CPU Type (8088, 8086, 80186, 80286, 80386, 80486): ___________________ ISA/EISA/PS2 Databus (if you don't know, assume ISA): ________________ BBS brand and version number: ________________________________________ Is your BBS software registered and paid for? ________________________ Drive:\Path\ to your BBS Master File: ________________________________ Drive:\Path\ to your UTI programs: ___________________________________ Drive:\Path\ to your DataMail programs: ______________________________ Drive:\Path\ to your DataMail uploads: _______________________________ DOS version number & manufacturer: ___________________________________ DesqView / Windows / LAN version, number of windows active, window configuration info, etc.: ____________________________________________ ____________________________________________ ____________________________________________ TSR's & Device Drivers loaded: _______________________________________ _______________________________________ _______________________________________ Front-end program (if any) and parameters: ___________________________ ___________________________ Is your DTE/DCE speed locked? ________________________________________ If so, do you have RTS/CTS handshaking active? _______________________ Parameters to SHARE.EXE in your CONFIG.SYS: __________________________ Number of FILES & BUFFERS in CONFIG.SYS: _____________________________ State exact nature of problem. Include all symptoms, such as when the problem occurs & when it doesn't, number of nodes active & online, etc. If related to file transfers, list your file transfer batch file for me please, and DMXFERS.TXT. Use additonal sheets if required. If possible, provide a sample screen-capture of events leading up to the problem, and the contents of DMLOG.x: ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ Please send the above information to: Richard K. Naff 2023 Shortal Drive Dallas, TX 75217-1834